🤖 Package update #1168
Merged
🤖 Package update #1168
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I have just re-triggered the update to (hopefully) include the new fakenet release (released yesterday). |
vm-packages
force-pushed
the
package-update
branch
from
bb7df70 to
e2f5245
Compare
|
It seems fakenet is also affected by #1162 |
|
Re-triggering now that #1162 has been merged! |
vm-packages
force-pushed
the
package-update
branch
from
e2f5245 to
79e5c2d
Compare
|
@sara-rn your fix worked, look how many updates! 😮 |
|
Testing... |
Ana06
approved these changes
Nov 22, 2024
There was a problem hiding this comment.
I have tested all the packages and I think it is good to go! 🚢
- azurehound.vm to 2.2.1, noticed the issue already reported in AzureHound is a console application #784 but it is unrelated to the update
- chainsaw.vm to 2.10.1, missing a dependency, error was present in previous version too so it is independent to the update. Documented in chainsaw is missing a dependency #1171.
- cyberchef.vm to 10.19.4, it seems to work fine
- dnspyex.vm to 6.5.1, it seems to work fine
- dokan.vm to 2.2.0.1000, it seems to be ok
- fakenet-ng.vm to 3.3, it seems to work fine
- goresym.vm to 3.0.1, it seems to work fine
- pdbresym.vm to 1.3.6, it seems to work fine. I have also tested
pdbs.pdbresym.vmas this package is an important dependency and that seems to work fine too. - sclauncher.vm to 0.0.6, it seems to work fine
- sclauncher64.vm to 0.0.6, it seems to work fine
- seclists.vm to 2024.4 this tool does not have a
.exeassociated with it, so this links it to the directory and it looks ok - sharphound.vm to 2.5.8, message in the output that is also present in the previous version:
We can merge this PR as the info/error is present without the update too, but I am not familiar with the tool to know if this is something we should fix. @mandiant/commando-vm can you please check and open an issue if this is a bug so that we have it tracked? - tor-browser.vm to 14.0.2, it creates a shortcut in the desktop it should not create. It is a minor issue, documented in tor-bowser.vm creates shortcut in Desktop #1172.
- total-registry.vm to 0.9.7.9, it seems to work fine
- vscode.vm to 1.95.3, it seems to work fine
- windows-terminal.vm to 1.21.3231.0, it seems to work fine
- wireshark.vm to 4.4.2, it seems to work fine
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Automated package update created by update_packages.yml. Note the update is triggered weekly and will modify this PR if it has not been merged.